docs: add Dockerfile auto-discovery workflow pattern #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add documentation for automatically discovering Dockerfiles in repos with multiple Dockerfile locations. Uses a two-job workflow pattern where the first job finds Dockerfiles matching common patterns (Dockerfile, Dockerfile.*, *.dockerfile) while excluding test fixtures and build artifacts, then passes discovered paths to the scan job. This approach was chosen over building discovery into Socket Basics itself for better portability and per-repo customization.
dacoburn
approved these changes
Feb 4, 2026
pvdz
approved these changes
Feb 4, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds documentation for automatically discovering Dockerfiles in repositories with multiple Dockerfile locations, eliminating the need to manually list each path.
Dockerfile,Dockerfile.*,*.dockerfileContext
This documents the GitHub Actions approach discussed in #19, which was preferred over building discovery into Socket Basics itself for portability and per-repo customization.
Test plan